feat: EKS 1.35 upgrade — eks_standard default + version enum#355
Closed
AbhisHub-12 wants to merge 1 commit into
Closed
feat: EKS 1.35 upgrade — eks_standard default + version enum#355AbhisHub-12 wants to merge 1 commit into
AbhisHub-12 wants to merge 1 commit into
Conversation
…o 1.37 Bump eks_standard cluster_version default 1.34 -> 1.35 (matching the EKS/AKS 1.35 rollout) and align the facets.yaml version enum with the variables.tf validation (which already allows up to 1.37) by adding 1.36 and 1.37. - sample.spec.cluster_version: 1.34 -> 1.35 - spec.cluster_version.default: 1.34 -> 1.35 - spec.cluster_version.enum: add 1.36, 1.37 (was capped at 1.35)
Collaborator
|
already moved to 1.36 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Upgrades the
kubernetes_cluster/eks_standardmodule to Kubernetes 1.35 and fixes a version-list inconsistency.cluster_versioneks_standard/1.0/facets.yaml:921.341.35cluster_versioneks_standard/1.0/facets.yaml:2311.341.35eks_standard/1.0/facets.yaml:233-2411.351.36,1.37Why
facets-iac(#2100, #2103).variables.tf:50, whosecontains([...])validation already allows1.28–1.37. Users couldn't select1.36/1.37in the UI even though the module accepted them. Extending the enum resolves the mismatch.Why this is the only code change needed
This catalog is forward-compatible by design — the rest of the fleet needs no edits for 1.35:
cluster_version(AWS Auto Mode manages it).1.35; vke alreadyv1.35.0+1.AL2023(correct for K8s 1.33+).latest— AWS auto-manages them per cluster version.Verify-only (no code change; user-controllable defaults, flagged for awareness)
Confirm compatibility with K8s 1.35 — these have no enum, users set them:
1.5.03.0.02.4.61.3.4Validation
raptor create iac-module --dry-run:✅ Terraform validation successful (schema/structure — the part this change touches).
AWS-0039(HIGH) — EKS secret encryption not enabled —main.tf:35-188AWS-0104(CRITICAL) — security group allows unrestricted egress —main.tf:250These exist in the vendored
aws-terraform-eksmodule independent of this change. Out of scope for a version upgrade; left for a dedicated hardening PR.Test plan
1.35default renders in the module UI dropdown with1.36/1.37selectableeks_standardcluster at1.35on a dev environment